Interactive social media access to data systems

ABSTRACT

Provided are techniques for interactive social media access to data systems. A social media gateway interface with adapters for each of multiple social media applications is provided. An event is published from a data system to at least one of the multiple social media applications. A social media bot is created to represent the data system. The social media bot and one of the adapters are used to enable the data system to interact with at least one of the multiple social media applications.

FIELD

Embodiments of the invention relate to interactive social media accessto data systems, such as Extract Transform and Load (ETL) servers,Master Data Management (MDM) servers, data stores, data warehouses, etc.

BACKGROUND

Extract Transform and Load (ETL) servers may be described as ones thatextract data from a source, transform the data, and load the data backto the source or to a target. Master Data Management (MDM) servers maybe described as managing enterprise data and providing a Single Sourceof Truth (SSoT). Single Source of Truth (SSoT) may be described asstructuring information models so that each data element is stored once(i.e., there are no duplicates stored), but there may be many referencesto the data element.

Access to ETL and MDM servers today is for the most part closed andhighly specialized. ETL and MDM tool user interfaces are complex andrequire extensive training to use. This prevents the use of ETL and MDMservers from becoming more commonplace.

In addition, today, even a simple problem, such as duplicate records,may hold up an entire data upload process for MDM servers. Also, ifmultiple participants need to be contacted to solve a problem, the timeto resolution can increase exponentially.

Existing ETL tools offer a Graphical User Interface (GUI) for ETLcomponent (e.g., job) design, administration, and monitoring. The GUIfor ETL component design and monitoring may be complicated, so thatcustomers typically need to undergo training before they can use the GUIand often engage services of experts.

The ETL tool development team may struggle to keep up with ever evolvingGUI technologies. Changing the GUI to these new GUI technologies may betime-consuming and expensive. Also, each time the ETL tool changes theGUI interface, customers undergo an often steep learning curve beforethey can use the GUI.

Developing mobile applications for the ETL tools may be difficultbecause of the complexity, plethora of devices to support, lack ofmobile development skills, and significant time to design mobile userinterfaces. As a result, the technology of the ETL GUIs may lag behindthe rest of the industry.

Furthermore, the ETL tools are not leveraged as a tool to provide mobileusers access to their data in their databases, data warehouses, or otherdata sources.

Existing MDM tools also offer a Graphical User Interface (GUI) formonitoring and administration. The GUI interface is typically a bespokeMDM interface that requires training, is accessed apart from normalbusiness processes, and/or is embedded in other places not associatedwith a GUI used regularly by daily users.

SUMMARY

Provided is a method for interactive social media access to datasystems. The method comprises: providing, with a processor of acomputer, a social media gateway interface with adapters for each ofmultiple social media applications; publishing an event from a datasystem to at least one of the multiple social media applications;creating a social media bot to represent the data system; and using thesocial media bot and one of the adapters to enable the data system tointeract with at least one of the multiple social media applications.

Provided is a computer program product for interactive social mediaaccess to data systems. The computer program product comprising acomputer readable storage medium having program code embodied therewith,the program code executable by at least one processor to perform:providing, by the at least one processor, a social media gatewayinterface with adapters for each of multiple social media applications;publishing, by the at least one processor, an event from a data systemto at least one of the multiple social media applications; creating, bythe at least one processor, a social media bot to represent the datasystem; and using, by the at least one processor, the social media botand one of the adapters to enable the data system to interact with atleast one of the multiple social media applications.

Provided is a computer system for interactive social media access todata systems. The computer system comprises: one or more processors, oneor more computer-readable memories and one or more computer-readable,tangible storage devices; and program instructions, stored on at leastone of the one or more computer-readable, tangible storage devices forexecution by at least one of the one or more processors via at least oneof the one or more memories, to perform operations, the operationscomprising: providing a social media gateway interface with adapters foreach of multiple social media applications; publishing an event from adata system to at least one of the multiple social media applications;creating a social media bot to represent the data system; and using thesocial media bot and one of the adapters to enable the data system tointeract with at least one of the multiple social media applications.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

In the drawings, like reference numbers represent corresponding partsthroughout.

FIG. 1 illustrates, in a block diagram, a computing environment inaccordance with certain embodiments.

FIG. 2 illustrates an example for duplicate record resolution inaccordance with certain embodiments.

FIG. 3 illustrates another example for duplicate record resolution inaccordance with certain embodiments.

FIG. 4 illustrates an example of how a social media interface gatewaymanages the ETL and MDM events in accordance with certain embodiments.

FIG. 5 illustrates, in a flow diagram, operations for event processingin accordance with certain embodiments.

FIG. 6 illustrates, in a flow diagram, operations for interactions withsocial media applications in accordance with certain embodiments.

FIG. 7 illustrates use of a social media bot to resolve a problem inaccordance with certain embodiments.

FIG. 8 illustrates an example chat session and example REST calls inaccordance with certain embodiments.

FIG. 9 illustrates a snippet of WADL for an ETL “users” collection inaccordance with certain embodiments.

FIG. 10 illustrates a collection grammar for a “users” instance “user”in “user.xsd” in accordance with certain embodiments.

FIG. 11 illustrates a table illustrating a data store entry for aresource “users” GET in accordance with certain embodiments.

FIG. 12 illustrates an example of a chat to REST mapping data storeentries in accordance with certain embodiments.

FIG. 13 illustrates, in a flow diagram, operations for using message toREST mappings in accordance with certain embodiments.

FIG. 14 illustrates components to implement an ETL group chat session inaccordance with certain embodiments.

FIG. 15 illustrates flow between components in accordance with certainembodiments.

FIG. 16 illustrates, in a flow diagram, operations for personifying datasystem components using chatbots in accordance with certain embodiments.

FIG. 17 illustrates, in a block diagram, a computer architecture thatmay be used in accordance with certain embodiments.

DETAILED DESCRIPTION

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

Interactive Social Media Access to Data Systems

Embodiments both simplify and broaden the reach of data systems, such asExtract Transform and Load (ETL) servers, Master Data Management (MDM)servers, data stores, data warehouses, etc. Embodiments create a genericsocial media wrapper framework for such data systems.

Although embodiments and examples herein may refer to ETL and MDMservers and components merely to enhance understanding, embodiments areapplicable to other types of data systems and components (e.g.,projects, jobs, stages, or administration processes).

Social media applications include, for example, a social media bot(e.g., representing a chatbot, blogs, posts, Rich Site Summary (RSS)feeds, wikis, microblogging services (e.g., that issue broadcastmessages), social networking services (e.g., for data sharing), voicerecognition systems, Artificial Intelligence (AI) systems, InstantMessage (IM) systems, sametime systems, Short Message Service (SMS)systems, enterprise software service, self-help service, etc.

Social media concepts are about information sharing, simplicity, andpersonalization, and are part of the wider World Wide Web (WWW) 2.0umbrella. Use of social media in society today is becoming moreprevalent as a 24×7 means of communication with friends, family, andco-workers. In the workplace, employees work remotely, but stayconnected using social media, from a variety of devices, such as smartphones.

Embodiments enable ETL and MDM servers to be accessible via social mediaapplications, so that ETL and MDM servers may be accessed by customerswhen and where they need their data, using tooling they already know.Furthermore, social media applications may reap benefits from using ETLand MDM functions, such as using the ETL tools to analyze the data andprovide insights or using the MDM server to provide a single source oftruth. Embodiments integrate social media applications with existing ETLand MDM servers, without rewriting the ETL and MDM servers.

Embodiments provide interface mappings that allow data systems to beaccessed in a social media setting via a social media interaction(message) that is converted into a request for the data system.

Embodiments map between social media interfaces such as chat messages,and Representational State Transfer (REST) interfaces to data systems,in an automated fashion, leveraging a number of REST features, includingthe Web Application Descriptor Language (WADL).

Embodiments enable social media access to data systems, thus broadeningthe reach of data system products. FIG. 1 illustrates, in a blockdiagram, a computing environment in accordance with certain embodiments.A social media interface gateway 110 is coupled to a network 100 and todata systems 140. The data systems 140 include an Extract Transform andLoad (ETL) server 150, a Master Data Management (MDM) server 160, a datastore 170, and a data warehouse 180. Also, an event gateway 130 iscoupled to the social media interface gateway 110 for sending events tosocial media applications (e.g., via smart phone, chats, blogs, posts,RSS feeds, wikis, etc.). The events may be messages or notificationsthat the data systems 140 send to social media applications. Withembodiments, the social media interface gateway 110 is added to anexisting data system 140 to provide social media access to and from thedata system 140. The social media interface gateway 110 acts as a socialmedia wrapper for the existing data systems 140. Embodiments provide thesocial media interface gateway 110 and event gateway 130 to enablesocial media applications to interact with the existing data systems140.

Embodiments create a way to interface between a social mediaapplication, such as a chat application, and data system components, bycreating the social media interface gateway 110 (e.g., a social mediarobot or “social media bot” to REST proxy server). Embodiments define asocial media interface gateway for social media bots at the level of theREST resource (e.g., “projects”, “jobs”, “users”, etc.) and provide amapping between them. Embodiments provide a generic, dynamic mechanismof generating social media messages (e.g., chat messages) to and fromREST interfaces.

Embodiments apply to all social media applications, with an adapter(e.g., a “plug-in”) for each different type of social media application.In certain embodiments, a social media bot is associated with anadapter. FIG. 1 illustrates some example adapters 120 a, 120 b, 120 c,120 d, 120 e, and 120 f (“120 a-120 f”), and there may be otheradapters. Note that while the social media application adapters areprovided by embodiments, underneath, the layer to access the datasystems 140 is shared (i.e., common). This common layer uses theexternal interfaces to the data systems 140 to access them, includingindustry standard technologies such as HyperText Transfer Protocol(HTTP) Representational State Transfer (REST).

FIG. 1 represents a base architecture of social media applicationsinteracting with the data systems 140, with example social mediaapplication types in a pluggable architecture.

The social media interface gateway 110 contains pluggable social mediacomponents 120 a-120 f and provides a direct interface from the socialmedia to the data systems 140. For example, a chatbot may beinstantiated in the social media interface gateway 110 to represent theETL server 150 or the MDM server 160. A social media timeline mayindicate important events for the ETL server 150 or the MDM server 160,and notifications may be used as a way to resolve problems.

Furthermore, the data systems 140 may use multiple social media based oncurrent or past conditions or events. For example, immediate problemresolution may warrant opening up a chat channel with a customer supportrepresentative and showing the customer support representative the issuedirectly so that the customer support representative may take action. Abroader notification/broadcast may warrant issuing a message from thedata systems 140. These social media bots access the data systems 140,using interfaces such as the industry standard HTTP REST interface,which may be self-describing with addition of Web ApplicationDescription Language (WADL). In addition to the social media bot, thesocial media interface gateway 110 also has the ability to analyzeincoming social media (e.g., chat) messages and generate responses.

In certain embodiments, the social media interface gateway 110 uses acustomizable mapping table of the social media messages (e.g., chatmessage) and dialect to the data systems 140. Mappings may beautomatically generated from the interface itself. The social mediainterface gateway 110 allows social/mobile users to run/invoke/interactwith the data systems 140 components via third party social mediaapplications.

The event gateway 130 stores data system 140 events and provides theevents to subscribed social media application users. The event gateway130 may issue queries into the data systems 140 using the knowninterface (e.g., REST), as well as, register event endpoints with thedata systems 140. In certain embodiments, the event gateway 130 alsocontains a message queue and may provide events for social mediaapplication adapters in the social media interface gateway 110. Forexample, a notification may be made to update a social media groupstatus when an ETL component has failed or has completed.

Embodiments provide an interactive social media interface (via thesocial media interface gateway 110 and event gateway 130) that providesaccess to and from existing data systems 140. Embodiments offer morefunctionality than is otherwise available for the data systems 140 andenable easy access from mobile devices and other forms of access,including voice.

With embodiments, an ETL server 150, an MDM server 160, and/or otherdata systems 140 interactively participate in a social media setting.

Embodiments simplify ETL and MDM server usage and integrate such usageinto the social media and mobile world. This enables increased reach andfrequency of ETL and MDM use.

Using core characteristics of social media, embodiments enable thefollowing social media features for the data systems 140:

-   -   Create, share, and exchange information, content, and ideas in        virtual communities and networks. Embodiments create an        interactive data system participant in a social media setting        (e.g., a virtual person who can chat, post, etc.). For example,        one could pose questions to a company's ETL server 150 or MDM        server 160 via social media. Information may be conveyed via an        ETL and MDM social media page, including items such as an image        of a component with “map” like navigation, bringing up the stage        of interest when clicked. Additional links to standard tooling        may also be provided via the social media. With embodiments, the        basic enablement of social media for the data systems 140 is via        a new framework that adds a social media interface to the        existing data systems 140. The framework is flexible and        supports multiple social media adapters.    -   Interact: Embodiments allow social media to interact directly in        a 2-way conversation, with the data systems 140 via the social        media interface gateway 110.    -   Notify: Embodiments create the event gateway 130 that allows        interested parties to receive events over social media.    -   Co-create/collaboration: End users of collaborative social media        (e.g., group chat) may work together to create items (such as        ETL components) or resolve problems (such as de-duplication of        MDM upload).    -   Discuss: A voice gateway provides voice interactions with the        data systems 140.

In certain embodiments, the voice gateway is an adapter. In certainother embodiments, the voice gateway is a tool used by the otheradapters.

The following is a collection of example methods that comprise thesocial media system for the data systems 140.

-   -   Personalizing data system components as social media bots in a        smart phone group chat session. For example, this method creates        a persona for an ETL or MDM component to interact with an end        user in a chat session.    -   Social media bot to Representational State Transfer (REST) proxy        for the data system 140. For example, this method automatically        maps between social media and an ETL server 150 or an MDM server        160 using a social media bot-REST mapping capability.    -   Map a data system command line interface to a social media bot.        For example, this method creates a mapping from the social media        bot to an ETL command line utility and an MDM command line        utility.    -   Voice gateway interface to data systems 140. For example, this        method uses voice as one of the social media gateways, thus,        enabling a voice to ETL and MDM capability.    -   Voice print biometrics to access the data systems 140. For        example, this method is for identification, personalization, and        security for a voice to ETL and MDM path.    -   Natural Language Understanding (NLU) for use in social media        with the data systems 140. For example, this method uses natural        language for the interactions with the ETL server 150 and the        MDM server 160 for more conversational social media, such as        chat or voice.    -   Tracking usage of the data systems 140 via social media. For        example, this method tracks usage of the ETL server 150 and the        MDM server 160 via social media. This method may be used for        basic feature usage statistics or problem determination.    -   Social media usage analysis for data systems 140. For example,        this method provides usage analysis for ETL and MDM interactions        to predict patterns and make recommendations of actions for the        end user. Access to history of usage may be used to improve the        actions and responses of social media bots.    -   Social media dialect (e.g., chat) for the data systems 140. For        example, this method creates a dialect/language for social media        (e.g., chat) that is ETL and MDM specific.    -   Social media detection and modality switch during a data system        interaction. For example, this method provides an ability to        detect and switch social modality in a multi-modality        environment, based on conditions, such as type or amount of        information to convey to end user, or urgency of information.

Embodiments provide a complete social media system. Use of social mediafor the data systems 140 now enables communication with the data systems140.

Merely to enhance understanding of embodiments, some examples areprovided herein. For example, a process to remove duplicates from MDMdata may be integrated across a variety of social media. In this way,the appropriate media is chosen to best solve each interaction. The MDMserver 160 is given a “voice” in this process, as the MDM server 160,via a social media bot interface, and may interact in this social mediasetting as if it were a person. This interaction may include interfacingwith other social media as well as actual people. Furthermore, thistechnique enables multiple people to help resolve an issue as needed.Use of social media in this way reduces the time to resolve issues andimproves the overall communication between the MDM server 160 and users.

FIG. 2 illustrates an example for duplicate record resolution inaccordance with certain embodiments. In FIG. 2, the following path isused: using an MDM server 160→social networking service adapter 120d→social networking bot 260→social networking service web site 210 path.In FIG. 2, the MDM server 160 has detected duplicate records whileprocessing and the following processing occurs:

1. The MDM server 160, through social networking service 120 d, uses asocial networking bot 260 to post an event “Duplicate detected message#456” to the social networking web site 210.

2. An MDM administrator, “User” 220 (chat participant 1), sees thismessage and clicks on the message link. In response to the click on thelink, a chat session 200 is created. An MDM chatbot 250 is created toparticipate in the chat session 200 on behalf of the MDM server 160 (theoriginator of the event). The MDM server 160 may be described as aregular chat user on the User 220 chat application. The User 220 mayinvite the MDM server 160 to start a chat, which creates the MDM chatbot250. A chatbot may be described as a chat robot. The MDM chatbot 250will communicate to MDM server 160 through the chat adapter 120 b. Inparticular, the chat messages go from chat session 200←→MDM chatbot250←→chat adapter 120 b←→MDM server 160. That is, the chat messages arebi-directional. Likewise, the messages between user 220 and chat session200 are bi-directional. In this example, the chat session 200 betweenthe “User” 220 and the MDM chatbot 250 follows and quotes are used toidentify chat messages:

3. User 220: “For duplicate detected message #456, show items.

4. MDM chatbot 250:

-   -   “>John Doe 111 Main”    -   “>John Doe 111 Main, Austin, Tex. 78758”

5. The User 220 invites a peer, chat participant 2 230, to a group chat,along with the MDM chatbot 250. Chat participant 2 230 joins the chatsession 200.

6. User 220: “Chat participant 2 230, can you confirm and accept record2?”

7. Chat participant 2 230: “Sure”

8. User 220: “Show duplicate record detail”

9. MDM chatbot 250:

“Record 1:”

-   -   “Name: John Doe”    -   “Address: 111 Main”    -   “City: Austin”

“Record 2:”

-   -   “Name: John Doe”    -   “Address: 111 Main”    -   “State: TX”    -   “Zip: 78758”

10. Chat participant 2 230: “Accept City from Record 1; Accept State andZip from Record 2”

FIG. 3 illustrates another example for duplicate record resolution inaccordance with certain embodiments. In FIG. 3, the following path isused: a broadcast message 310→the message broadcast bot370→microblogging service adapter 120 c→MDM server 160.

In FIG. 3, the following processing occurs and quotes are used toidentify chat messages:

1. An MDM administrator 340 places a new file into an upload/scratchdata store 330 on a server. A user 342 may also participate in the chatsession 300. For example, the user 342 may be invited at step (9) belowto resolve issues.

2. The MDM administrator 340 posts a broadcast message 310 via amicroblogging service, for “New file of customers ready for upload”,along with instructions including “Analyze upload file for duplicates”and filename “customers.txt”. The message broadcast bot 370 receives thebroadcast message (which may be part of or work with the chat adapter120 b) and forwards the broadcast message 310 to the microbloggingservice adapter 120 c. In certain embodiments, this will be completedusing an application for the MDM administrator 340. The MDMadministrator 340 opens the application and selects the MDM server 160,which is shown as an application to the user. The message broadcast bot370 is created by the application to broadcast messages to the MDMserver 160 through the microblogging service adapter 120 c. Themicroblogging service adapter 120 c forwards the broadcast message 310to subscribers (who subscribe to the microblogging service).

3. The MDM server 160 is a subscriber and gets this broadcast message310.

4. The MDM server 160 starts the analysis on file “customers.txt”.

5. The MDM server 160 detects an issue, and, finding the MDMadministrator 340 online, starts a chat session 300 with the MDMadministrator 340 through the chat adapter 120 b and MDM chatbot 350.The chat messages go between: the MDM server 160←→chat adapter 120b←→MDM chatbot 350←→chat session 300.

6. MDM chatbot 350: “The customers.txt file has 14 new records and 3duplicate records”

7. MDM administrator 340: “Show the 3 duplicate records”

8. MDM chatbot 350: “Joe Smith, Joseph Smith, Joey Smith”

9. MDM administrator 340: “Resolve duplicates in the source file”

10. MDM administrator 340: “MDM chatbot 350, load the source file”

11. MDM chatbot 350 sends a message to the MDM sever 160 through thechat adapter 120 b, and the MDM server 160 loads the file without error.

12. The MDM server 160 sends a message to the social networking serviceadapter 120 d to update the status. The messages goes from: MDM server160→social networking service adapter 120 d→social networking bot360→social networking service web site 320. In this example, the MDM ssocial networking bot 360 posts, to the social networking web site 320timeline, a message that the new file of customers was created and that3 duplicate issues were resolved.

In the following example, there is a path from Customer call→Chat→SocialNetworking Service. In this example, a “User” gets a call about customerB. Turner, and wishes to add him as a friend to his personal datasharing web site page, but the User needs to obtain more detailedcontact information for B. Turner first. The User uses the social mediagateway 110 to ask the MDM server 160 to look up the customer record forB. Turner. The MDM record indicates that B. Turner is a preferredcustomer. So, via the MDM chatbot, the User adds B. Turner to his datasharing web site page as a preferred customer.

1. User starts up a chat session to the MDM server 160.

2. User: “Show me B. Turner.”

3. MDM chatbot:

-   -   “Record 1:”        -   “Preferred Customer: YES”        -   “Name: B. Turner”        -   “Address: 111 Main”        -   “City: Austin”

4. User: “Add B. Turner to my data sharing web site.”

5. The MDM data sharing bot adds B. Turner to User's data sharing website. Because B. Turner is a preferred customer, he is added to theUser's “Preferred Customer” list.

FIG. 4 illustrates an example of how the social media interface gateway110 manages the ETL and MDM events in accordance with certainembodiments. First, the system administrator 400 uses a subscriptionmanagement system 410 to register events that are to be subscribed fromthe ETL server 150 and the MDM server 160 and which users can accesswhat ETL and MDM events on which social media applications. Second, theETL and MDM event REST interface 450 allows the social media interfacegateway 110 to register what events need to be published from the ETLserver 150 and MDM server 160 Third, the ETL server 150 and the MDMserver 160 publish the subscribed events to the message queue 430managed by the social media interface gateway 110. Fourth, the socialmedia interface gateway 110 dispatches the received events to varioussocial media applications for different users 460, 462, 464 based on thesubscription information via adapters 120 a-120 f. In certainembodiments, there is one adapter implemented for one social mediaapplication in the social media interface gateway 110 to handle how toconnect to the social media application and how to send events to thesocial media application.

FIG. 5 illustrates, in a flow diagram, operations for event processingin accordance with certain embodiments. Control begins at block 500 witheach of multiple social media applications subscribing to one or moreevents. In block 502, in response to an event being published to amessage queue, the event is routed to the subscribed social mediaapplications via an adapter.

FIG. 6 illustrates, in a flow diagram, operations for interactions withsocial media applications in accordance with certain embodiments.Control begins at block 600 with a social media gateway interface withadapters for each of multiple social media applications being provided.In block 602, an event is published from a data system (e.g., an ETLserver, an MDM server, a data store, a data warehouse, etc.). In block604, a social media bot is created to represent the data system. Inblock 606, the social media bot is used to enable the data system tointeract with one or more social media applications.

Embodiments provide a generic, broad, social media wrapper/framework forthe existing data systems 140. For example, embodiments provide a way tointeractively participate with social media applications, personify ETLand MDM components, tasks, and data sources as social media bots, allowinteraction between bots and other social media participant end users,as well as, switch social media types based on the interactions.

Embodiments bring social media and data systems 140 together.Embodiments, use industry standard techniques for this integration.

Embodiments raise data system 140 into a new dimension of use.Embodiments make the data systems 140 easier to use and access and makeit easy for social media users to integrate data systems 140 into theirapplications.

Embodiments deal with a broad set of social media applications, such as,chat, blogs, posts, RSS feeds, wikis, enterprise software, etc. Tosupport various social media, embodiments define common layers,interfaces, and frameworks to deal with mapping ETL engine ApplicationProgramming Interfaces (APIs)/Components to messages, chats, voice, etc.

For example, embodiments monitor and control the ETL component runs.

Embodiments also allow users to create, design, and modify various ETLcomponents. Furthermore, with embodiments, ETL and/or MDM servers becomeinteractive social media participants.

Embodiments also set up an event gateway 130 (e.g., an event monitoringsystem) based on a subscription model to deal with securities anddelivering messages to different social media applications. Embodimentsprovide an event gateway 130 to control how each data system componentsends events at real time to the event monitoring system rather thanpolling operational databases.

Embodiments create a bi-directional social media interface gateway 110on top of the existing data systems 140, so that the data systems 140may interact directly with social media systems, via, for example, useof social media bots.

Embodiments use a social media platform to aid in a number of processesin the data system landscape, by allowing an interactive interface thatprovides access to and from the existing data systems 140.

For example, embodiments virtualize the ETL server 150 and the MDMserver 160 as a virtual person to participate in social media.Embodiments use one or multiple social media as an interface to interactand collaborative with real persons to resolve tasks in the ETL server150 and the MDM server 160. Embodiments introduce the use of a socialmedia interface gateway 110 with a dedicated adapter for each specificsocial media that will integrate social media and the ETL server 150 andthe MDM server 160. Embodiments provide the ETL server 150 and the MDMserver 160 a dialect to speak in social media. Embodiments providesubscribe management for ETL and MDM events. Embodiments selectively usethe best social media to conduct an ETL or MDM task. Embodiments usesocial media for ETL and MDM server usage tracking and analysis.

Embodiments provide a pluggable social media component for accessing anApplication Programming Interface (API) by providing an interfacesupporting pluggable social media components to access an API. Thepluggable social media components include, for example, a social mediabot, a voice recognition system, an artificial intelligence (AI), aninstant message (IM), a sametime, a short message service (SMS), asocial web, chat, blog, service, self-help service, rich site summary(RSS) feeds, etc. In certain embodiments, the API supports servicesselected from a group consisting of ETL services, subscribe services,register services, tracking services, analysis services, MDM services,etc. In certain embodiments, the interface utilizes a first messagequeue for interacting with social media components and a second messagequeue for the API.

Social Media Bot to Representational State Transfer (REST) Proxy forData Systems

Merely to enhance understanding, examples may be provided herein withreference to ETL components, however, embodiments also apply to otherdata system components and to data system data sources.

Embodiments provide a “social media bot” to “REST” proxy service withthe social media interface gateway 110. With embodiments, a systemadministrator selects which data system components (e.g., which ETL/MDMcomponents) to expose via existing REST resources. Interfaces to thesocial media bots (e.g., chat messages) are generated from these RESTresources. Use of the WADL description for REST services enables theautomation of this process. WADL is a feature automatically provided forREST resources. In certain embodiments WADL is written using the Java®API for REST resources (JAX-RS). (Java is a registered trademark ofOracle Corporation in the United States and/or other countries.) Via thegenerated social media bot messages, end users invoke the data systemfunctions from social media applications.

For example, chatbots participate in mobile chat sessions as virtualchat participants accepting input from chat participants (e.g., humanusers). To perform data system functions, a chatbot uses the data systemREST services and presents the results from the REST calls as chatmessages back to the chat participants.

Embodiments use social media to select and invoke existing data systemcomponents via REST services. The social media application may be anexisting mobile chat application. With embodiments, social applicationsallow multiple users to participate in a group chat session to work withexisting data system components (via REST resources) interactively andcollaboratively using plain instructions, commands, or voice.

Embodiments present a new way of invoking data system components fromsocial media and mobile platforms using a new social media bot-RESTproxy. This REST proxy converts the input expected by REST into socialmedia messages posed as questions to end users (e.g., chat questions).Information in the end user responses is used to issue the REST calls tothe data system components in the data system server. In turn, thesocial media bot-REST proxy converts the output from the REST calls intomessages for display in social media applications.

With embodiments, social media bots are automatically generated fromREST resources defined by WADL, rather than hand coded. This saves timeand effort to expose data system components to social mediaapplications.

With embodiments, there is no need to change existing data systems ortheir REST services to run within social media applications.

With embodiments, a mapping table of social media messages to REST callsis created and may be updated at any time without affecting the overallsystem operation. The mapping table may be customized further by userprovided message processing.

In certain embodiments, end users may interact with data systemcomponents via a mapping layer to their REST interfaces, using a socialmedia application. An example of such an application may be a group chatapplication that runs on a smart phone. Under the covers, these chatmessages are mapped to REST calls and vice versa.

Embodiments may return the description of the REST resource in WADL.This description may be obtained “live” via a run-time request or it maybe static. With embodiments, the description defines the operations thatmay be performed on the resource, as well as, the expected inputs andoutputs. This discovery may be performed by a system administrator orvia done automatically with tooling.

Using the WADL, the REST resources are registered in a social media botregistry and a user access control data store as data system componentsfor use by the social media interface gateway 110.

A system administrator may also set up the access privileges to specifywho can invoke the data system components and what users may do witheach REST API. This may be done using a web application, a stand-alonetool, or a mobile application.

For example, a chat middleware participates in the social mediaapplication as a “bot” representing an instance of a data systemcomponent. The data system component is assigned a name based on theREST resource name and instance, along with any configured namingconventions.

End users may invite these registered bots to a social media application(e.g., a group chat session) using the chat middleware.

When an end user sends a social media message (e.g., chat message) to asocial media bot, with embodiments, a chat message mapper converts thesocial media message to a REST call using a mapping data store.

The mapping to REST mapping data store may be further customized byusers (e.g., a system administrator) to improve the social media botmessages. Additionally, a callout may be utilized to external componentswith enhanced grammar matching capabilities to further improve thesocial message matching and generation capabilities. For interactivesocial media, such as chat, this provides a more natural/conversationaldialog for the chat messages. For example, instead of the chat message“get users” one could say “can I have a list of users” or “what usersare there”.

When the social media bot wishes to send a social media message (e.g.,chat message) back to the other chat participants, the social media botuses the message to REST mapping data store to convert the REST responseback to another social media message (e.g., a chat message).

For example, a common problem is that a system administrator forgets toset credentials for an ETL or MDM server. The problem appears in thefollowing manner. UserA tries to access the ETL or MDM server andreports that she used “GINGER” as the host name of a services tier andthe user/password “isadmin” and received the error: “No credentials werefound on the Services Tier for the specified user (‘isadmin’) forGINGER:31538”. For this example, the system administrator was in adifferent time zone, and had gone home for the day. In such cases, USERAmay spend a great deal of time trying to resolve the problem and mayhave to wait until the next day to find out that a simple credentialmapping had not been performed. With embodiments, a system administratormay be notified via social media of this urgent event. Using a mobilephone, the system administrator may click on the received message linkto invoke a mobile group chat session to a bot on the ETL server to setthe right credentials.

FIG. 7 illustrates components to implement an ETL group chat session inaccordance with certain embodiments. Similar components may be used toimplement an MDM group chat session in other embodiments. Also, althoughthe illustration of FIG. 7 describes a chatbot, other embodiments areapplicable to other types of social media bots (for each type ofadapter).

A group chat server 750 is responsible for managing on-going group chatsessions and dealing with various concurrent access issues to the groupchat session. The group chat server 750 includes a group chat interface752 and a group chat session controller 754.

A social media interface gateway 110 includes a chat adapter 120 b, asocial media bot registry and user access control data store 710, and anETL-REST client 716. In certain embodiments, a chat adapter 120 b (e.g.,an ETL group chat adapter) for a chat application is the mediatingcomponent between the group chat server 750 and the ETL server 150. Thechat adapter 120 b includes a chat message mapper 712 and a chat-RESTmapping data store 714. Also, there is a chatbot 720 for interactionsbetween the chat adapter 120 and the group chat server 750. The ETLserver 150 includes an ETL server component 152. The chat-rest mappingdata store 714 store message to REST mappings for use in convertingbetween REST calls and social media messages.

In the example of FIG. 7, there are two human chat participants, chatparticipant A 760 and chat participant B 762.

FIG. 8 illustrates an example chat session 800 and example REST calls850 in accordance with certain embodiments.

With reference to FIGS. 7 and 8, the following example is provided.Initially, user A attempts to set up an ETL project. She can access theETL host ‘GINGER’, but is unable to set up her project and does not knowwhy. She sees an error message, but it is not clear what is wrong. AnETL component 152, via a social media bot for the microblogging serviceadapter 120 c, posts an event to the ETL server 150 on behalf of userA's failed attempt. The message is: “No Engine Credentials Found on theServices Tier #123”.

For this example, an ETL administrator user “User B” has gone home forthe day, but is notified via the message of this urgent event. Using amobile phone, User B clicks on the #123 message link. This invokes amobile group chat session to the chat bot 720 on the ETL server 150 (theoriginator of the event). The chat bot 720 is sent this message, and achat session between chat participant User B 762 and the chat bot 720follows and quotes are used to identify chat messages:

User B: “Show detail for message #123”

Chat Bot: “Issue #123: A message from user “User A” indicates that noengine credentials were found on the Services Tier for the specifieduser (‘isadmin’) on the Information Engine GINGER:31538.”

Using a problem determination symptom analysis data store, the chat bot720 finds that problem 123 means an Operating System (OS) user needs tobe assigned to the specified Information Services (IS) server user. Thechat bot 720 shows chat participant User B 762 the details for the ISserver user “isadmin” followed by the information for the engine'soperating system users on host GINGER and quotes are used to identifychat messages.

Chat Bot: “Showing IS user isadmin”

“Record 1:”

“Name: isadmin”

“OS user: none”

“OS user password: not set”

Chat Bot: “Showing engine GINGER OS users”

“admin”

“guest”

“Administrator”

User B: “Assign OS user admin to isadmin.

Chat Bot: “Enter password.”

User B: “******”

Chat Bot: “OS user admin assigned to isadmin.”

Chat Bot: “Should I show isadmin detail?”

User B: “yes”

Chat Bot: “Showing isadmin”

“Record 1:”

“Name: isadmin”

“OS user: admin”

“OS user password: confirmed”

User B: “Tell user that Issue #123 has been resolved.”

The chat bot 720 looks up user “User A” and locates a chat address. Thechat bot 720 invites User A to the chat session.

Chat Bot: “User A, Issue #123 has been resolved. Please confirm(Yes/No)?”

User A: “Yes. It works now! Thanks?”

Chat Bot: “Issue #123 removed.”

In certain embodiments, the group chat server 750 is responsible formanaging the on-going chat sessions. The group chat server 750 alsomanages concurrent access from multiple chat users in a chat session.

In certain embodiments, the social media interface gateway 110, whichincludes the chat adapter 120 b, is a gateway between the group chatserver 750 and data systems, such as the ETL server 150. The chatadapter 120 b allows social media users to invoke the ETL component 152on the ETL server 150, via a REST proxy, for social media applications(e.g., a chat application).

The social media bot registry and user access control data store 710 isa repository for registering REST resources to be exposed to the socialmedia applications as “social media bots”. The social media bot registryand user access control data store 710 also contains user registrationsand access privileges of each user to each registered REST resource.

The REST resource details are mapped into social media messages andplaced into the chat-REST mapping data store 714.

When REST resources are registered on the data system (e.g., ETL server150), the REST resources are analyzed using the site's WADL schema. FIG.9 illustrates a snippet of WADL 900 for an ETL “users” collection inaccordance with certain embodiments. This WADL 900 represents thedecomposed resource, media types, items, and defined actions/verbs. Fromthe WADL 900, there is a resource named “users” with an HTTP method“GET”. There are optional parameters of: “filter”, “sort”, “wadl”,“content-range”, and “uuid”. So this REST resource “users” with method“get” may translate to a chat message of “get users”. Also analternative, more user friendly/conversational message of “show userlist” may be provided.

Furthermore, from the WADL 900, the resource grammars and/or media typeinformation for the request input/output may be used. FIG. 10illustrates a collection grammar 1000 for a “users” instance “user” in“user.xsd” in accordance with certain embodiments. In certainembodiments, this is the item record schema for the user collection.

FIG. 11 illustrates a table 1100 illustrating a data store entry for aresource “users” GET in accordance with certain embodiments. ExtensibleMarkup Language (XML) has an XML Schema Definition (XSD). In FIG. 11,the data store entry is based on using the WADL 900 and item XSDillustrated in FIG. 10.

Additionally, the chat-REST mapping data store 714 may contain thefollowing features.

a) A single chat interaction may require multiple REST calls.

b) The chat-REST mapping data store 714 may be further customized byusers anytime, even at runtime, without affecting the operationalcharacteristics of the overall system.

c) For interactive social media, a more conversational set of messagesmay be desired. For such cases, an external entity, such as a NaturalLanguage Understanding (NLU) system may be used to create a moreconversational/user-friendly set of messages.

FIG. 12 illustrates an example of a chat to REST mapping data storeentries 1200 in accordance with certain embodiments.

In certain embodiments, an end user may invite a registered ETLcomponent chatbot to join a group chat session via the chatbot 720. Thegroup chat server 750 sends chat updates, notifications, and invitationsto participants to a chat session, such as the chatbot 720. To sendmessages, voices, images, etc. to a group chat session, chatparticipants use the group chat interface 752 exposed by the group chatserver 750.

Multiple concurrent chatbot instances may exist, and each chatbot mayrepresent a different REST resource instance.

The end user sends conversational chat messages to the chatbot for theETL component 152. The chatbot uses the chat message mapper 712 to mapchat messages into REST calls. The mapper uses the chat-REST mappingdata store 714 to do this conversion. The chatbot then uses the ETL RESTclient 716 to invoke the ETL component 152 on the ETL server 150. Thesame process may be used when the end user responds to a chat prompt.

Likewise, the chatbot 720 uses the REST client to receive aresponse/results from the ETL component 152. The chatbot 720 providesthe REST response to the chat message mapper 712 for conversion into aconversational chat message. The conversational messages are sent to themobile chat session via the group chat 752 and group chat server 750.

Embodiments automate services based on representational state transfer(REST) interfaces by providing a social media bot registry and useraccess control data store 710 for REST resources; providing a socialmedia interface gateway 110 allowing a user to access the REST resourcesbased on entered text; responsive to a user utilizing the social mediainterface gateway 110 and entering text, utilizing natural languageprocessing (NLP) to analyze the text for a REST resource in the socialmedia bot registry and user access control data store 710; and,responsive to identifying the REST resource, automatically accessing theREST resource based on the analyzed text.

In certain embodiments, the social media interface gateway 110 issupported on a social media selected from a group consisting of aninstant message (IM), a sametime, a short message service (SMS), asocial web site, chat, blog, service, self-help service, chat, blog,rich site summary (RSS) feeds, and etc.

In certain embodiments, the REST resource is for a service selected froma group consisting of ETL, subscribe, register, tracking, analysis, MDM,etc.

Personalizing Data System Components and Data Sources as Chatbots in aGroup Chat Session

Embodiments allow customers to use their existing social applications,which they are familiar with, to access data system tools. Inparticular, customers may now inspect, create, modify, administer, andmonitor the data system components using mobile applications, such as onsmart phones.

Mobile applications and social applications (e.g., on smart phones) arebecoming more popular. One such popular application is a group chatapplication. Embodiments leverage existing mobile applications andsocial applications, such as the group chat application, that customersalready know how to use, with data system tools.

Embodiments implement a solution for chat in the framework for datasystems 140. Embodiments create a collection of interactive group chatparticipants, also known as “chatbots”, that each represents a differentdata system component/data source. Furthermore, embodiments determinehow they work together and how they collaborate with end-user chatparticipants to solve problems.

Embodiments extend existing mobile group chat applications. Embodimentsenable data system component design, update, create, run, control, andotherwise administer data system components and access data in acollaborative way. Embodiments create and personify various data systemcomponents and data sources as virtual chat participants in a group chatsession, where different data system components and data sources arerepresented dynamically as different chatbots. In this manner, ETLcomponents and MDM components, for example, become interactive chatparticipants.

Embodiments enable creating, modifying, inspecting, administering, andmonitoring a data system component using a group chat application. Thedata system components (e.g., projects, jobs, stages, or administrationprocesses) are personified as chat robots, or chatbots. The data systemcomponents represented by the chatbots evolve during the group chatsessions based on the messages posted by customers (end users). Thechatbots representing the data system components may show images thatrepresent the data system component (such as overall ETL stage flowdiagrams), report the status of the data system job (such as job runstatus, error codes, and error messages), provide links to web pages,and invite another person (e.g., a customer support agent) to join achat session (e.g., if a problem arises).

Furthermore, embodiments personify data sources directly as chatbots sothat users may access to their data directly from their mobile chatapplications. For example, the ETL/MDM tool is leveraged at the back-endto run the data extraction or to run MDM jobs created in real time basedon user's inputs from mobile chat applications.

With embodiments, the data system GUI applications and solutions:

1. Use a mobile group chat to design and monitor data system jobdesigns. The mobile group chat may be an existing group chat applicationwith a virtual chat participation interface.

2. Personify data system components and data sources as group chatparticipants. The group chat allows multiple users to participate in thegroup session to work with their data or various data system componentsin an interactive and collaborative way using plain instructions,commands, or voice.

3. Provide mobile users 24×7 access to their data in their data sourcesand various features in the data systems.

4. Leverage features of existing chat applications to invite customersupport agents to a chat session for problem determination, should thecondition warrant. The customer support agents are provided the chathistory and information to help resolve the problem.

Merely to enhance understanding, examples will be provided herein withreference to ETL components, however, embodiments also apply to otherdata system components.

In one embodiment, when a customer wants to create, modify, inspect,run, or monitor an ETL job on an ETL server from a smart phone, thecustomer starts a mobile chat application and invites the ETL serverchatbot to the chat session. Through the chat session, customers maycreate, inspect, modify, administer, and/or monitor ETL components(e.g., projects and jobs). Each of the ETL components: ETL server,project, jobs, administration, and stages joins the chat session as adifferent chatbot. Thus, if there are 5 ETL components, there may be 5chatbots (one for each of the components).

In another embodiment, when a customer wants to access and discuss data,such as sales leads, from smart phones, the customer starts a mobilechat application and invites the ETL server chatbot to the chat session.The ETL server presents a list of data connections that it can access.For this example, the customer selects a customer system and asks forthe sales leads in the customer system. At the back-end, based on thecustomer's requirement, a data extraction job is created in real-time toextract the data from the lead object in the customer system. Theextraction result is presented to the customers as chat messages.

The following shows an example of how an ETL job may be created in agroup chat session:

1. A customer starts a group chat application on a smart phone.

2. The customer invites the ETL server chatbot “ETLSrv1” to a group chatsession. The “ETLSrv1” may be listed as a virtual user contact in theuser's contact list.

3. The customer types the chat message “ETLSrv1, open project “Emp” intothe chat application, and the chatbot “ETLSrv1” invites the chatbot“ETLProjEmp” to join the chat. The chatbot “ETLProjEmp” represents theETL project “Emp”.

4. The customer types the chate message “ETLProjEmp, create an ETL jobEmpUpdt”. The chatbot “ETLProjEmp” creates a new ETL job “EmpUpdt” andinvites a chatbot “ETLJobEmpUpdt” to join the group chat session.

5. The customer types the chat message “ETLSrv1, show all supportedstages”. The chatbot “ETLSrv1” lists all the stages supported by server:“Extensible Markup Language (XML), transformer, Sequential File, etc.with images.”

6. The customer types the chat message: “ETLJobEmpUpdt, add a sequentialFile stage input”. The chatbot “ETLJobEmpUpdt” adds the sequential filestage “input” to the ETL job and invites a new participant chatbot“input step” to the session.

7. Similarly to the processing of step 6, the customer adds anotheroperation of “transformation operation”, “output operation”, to the ETLjob. As each operation is added, an additional group chat participant(chatbot) that represents the operation is added.

8. The customer may use the same chat session to set up the stageproperties in similar fashion.

9. Finally, the customer types the chat message “ETLJobEmpUpdt, run” andthe ETL job runs to complete, and the chatbot “JobEmpUpdt” shows therunning results or failure messages in a chat session (e.g., in a chatwindow in which the participants are chatting).

The following is an example of how to use a data source chatbot toretrieve sales leads from the customer system in a mobile chat session:

1. A customer starts a group chat application on a smart phone.

2. The customer invites the ETL server chatbot “ETLSrv1” to a group chatsession. The “ETLSrv1” may be listed as a virtual user contact in theuser's contact list.

3. The customer types the chat message “ETLSrv1, show all the datasources” into the chat application, and the chatbot “ETLSrv1” shows allthe data sources supported by an ETL server in the chat session and asks“which data source you want to access?”. For example, the data sourcesmay be shared data connections created by various ETL connectors.

4. The customer types the chat message “ETLSrv1, access CustomerSystem”. The chatbot “ETLSrv1” invites a chatbot “Customer System” tojoin the chat session. The chatbot “Customer System” shows a list ofsupported data objects or queries and asks “which data do you want toknow?”

5. The customer types the chat message “Customer System, show me all thesales leads from Mar. 1, 2013 to now”. The chatbot “Customer System”lists all the sales leads created from Mar. 1, 2013 to now in the chatsession.

FIG. 14 illustrates components to implement an ETL group chat session inaccordance with certain embodiments. Similar components may be used toimplement an MDM group chat session in other embodiments.

A group chat server 1450 is responsible for managing on-going group chatsessions and dealing with various concurrent access issues to the groupchat session. The group chat server 1450 includes a group chat interface1452 and a group chat session controller 1454.

A chat adapter 120 b (e.g., an ETL group chat adapter) for a chatapplication is the mediating component between the group chat server1450 and the ETL server 150. The ETL server 150 includes an ETL jobimport interface 1402, an ETL design/monitor interface 1404, and an ETLadministration interface 1406. The chat adapter 120 b includes messagemapping definitions 1410 for chatbots, a chat content analyzer 1412, achat content generator 1414, and an ETL job generator 1416. The messagemapping definitions 1410 contain the incoming chat message templates1430 and outgoing chat message templates 1432.

The chat adapter 120 b invokes the ETL design/monitor interface 1404exposed by the ETL server 150 to design, modify, run, and monitor ETLjobs. The chat adapter 120 b may also interface with the ETLadministration interface 1406 to perform administration functions. Inaddition, the chat adapter 120 b uses the ETL job import interface 1402to import an new job into an ETL project. Moreover, the chat adapter 120b personifies the core ETL components, such as ETL projects/jobs and thedata sources that the ETL server 150 can access as chatbots and dependson the chatbots to participate in the group chat session.

The virtual chat participants (chatbots) include an ETL job chatbot1420, an ETL project chatbot 1422, and a customer system chatbot 1424.In certain embodiments, the chatbots 1420, 1422, and 1424 may beimplemented as part of the chat adapter 120 b. In other embodiments, thechatbots 1420, 1422, and 1424 may be implemented outside of the chatadapter 120 b.

The chatbots 1420, 1422, 1424 implement a chat participant interface1452 and join and participate in a group chat. The group chat server1450 sends chat updates and notifications and invites chatbots to agroup session through the chat participant interface.

For example, to send a message (which may include voice clips, filelinks, web pages, images, etc.) to a group chat session, a chatbotinvokes a group chat interface 1452 exposed by the group chat server1450. There are two kinds of chatbots: one kind representing various ETLcomponents (such as ETL jobs, projects, etc.) and another kindrepresenting various data sources (such as various databases). Thebehavior of a chatbot may be described in a state machine. The chatbotmoves from one state to other states based on the messages received fromthe group chat server 1450. At the same time, the chatbot takes actionswhen moving from one state to another. The code for each chatbot may begenerated from the state machine created for the chatbot.

The chat content analyzer 1412 analyzes a chat message and converts thechat message from the group chat server 1450 to a method invocation to achatbot 1420, 1422, 1424 based on the input chat message templates 1430for that chatbot. When a chatbot wants to create a chat message, thechatbot uses the chat content generator 1414 to formulate the chatmessage based on the outgoing chat message templates 1432 for thechatbot.

A message mapping definition 1410 for a chatbot contains the input chatmessage templates 1430 to define how to map an input message into amethod invocation based on pattern matching. The message mappingdefinition 1410 also contains the outgoing chat message templates 1432to define an outgoing chat message template 1430 responding to anincoming chat message. The outgoing chat message templates 1432 maybring video clip, image, text, etc. together to create an out-bound chatmessage. For example, an image may show the design tip at a particularmoment when mobile users are modifying a stage instance within an ETLjob.

The ETL job generator 1416 is responsible for creating ETL jobs based onuser's requirements. The mobile chat participants 1460, 1462 mayparticipate in a group chat session with chatbots 1420, 1422, 1424 viathe group chat server 1450.

The following sequence describes how a chatbot may work after receivinga message from the group chat server 1450:

1. A chatbot 1420, 1422, 1424 receives a message from a group chatserver 1450.

2. The chatbot 1420, 1422, 1424 converts the message into its own methodcall using the chat content analyzer 1412 and the input chat messagetemplates 1430 defined for the chatbot.

3. The chatbot 1420, 1422, 1424 performs its tasks in the method call,such as creating another chatbot, creating ETL jobs, calling ETLinterfaces, etc.

4. When the chatbot 1420, 1422, 1424 is ready to respond to the messagereceived from the group chat server 1450, the chatbot 1420, 1422, 1424uses the chat content generator 1414 to formulate a response based on anoutgoing chat message template 1419. The chatbot 1420, 1422, 1424 mayalso attach possible incoming chat message templates 1430 that it canaccept next to guide the mobile user's operations.

5. The chatbot 1420, 1422, 1424 sends the response back to the groupchat server 1450.

FIG. 15 illustrates flow 1500 between components in the FIG. 14 inaccordance with certain embodiments. In particular, FIG. 15 illustrateshow pieces are put together to retrieve sales leads using a generatedETL job and illustrates results as a chat message from a customer systemchatbot.

FIG. 16 illustrates, in a flow diagram, operations for personifying datasystem components using chatbots in accordance with certain embodiments.Control begins at block 1600 with a social media gateway interface witha chat adapter for a chat application being provided. In block 1602, oneor more chatbots that each represents a corresponding component of adata system are created. In block 1604, the one or more chatbots and thechatbot adapter are used to manage the corresponding components of thedata system.

Embodiments enable managing components of a data system by creating oneor more virtual chat participants (e.g., chatbots) of a social mediaenvironment (e.g., chat session) each representing a correspondingcomponent of the data system and interacting with the virtual chatparticipants in the social media environment to manage the correspondingcomponents of the data system. The virtual chat participants includechatbots (chat robots) to receive and process requests within the socialmedia environment for corresponding components of the data system. Amobile device may be used to access the social media environment andinteract with the virtual chat participants. The virtual chatparticipants may represent data sources. A customer support agent may beinvited to join the social media environment to address a problem withthe data system. The virtual chat participants may interact with eachother to perform data operations to manage the corresponding componentsof the data system.

FIG. 17 illustrates a computer architecture 1700 that may be used inaccordance with certain embodiments. In certain embodiments, the socialmedia interface gateway 110, the event gateway 130, the ETL server 150,and/or the MDM server 160 may implement computer architecture 1700. Thecomputer architecture 1700 is suitable for storing and/or executingprogram code and includes at least one processor 1702 coupled directlyor indirectly to memory elements 1704 through a system bus 1720. Thememory elements 1704 may include local memory employed during actualexecution of the program code, bulk storage, and cache memories whichprovide temporary storage of at least some program code in order toreduce the number of times code must be retrieved from bulk storageduring execution. The memory elements 1704 include an operating system1705 and one or more computer programs 1706.

Input/Output (I/O) devices 1712, 1714 (including but not limited tokeyboards, displays, pointing devices, etc.) may be coupled to thesystem either directly or through intervening I/O controllers 1710.

Network adapters 1708 may also be coupled to the system to enable thedata processing system to become coupled to other data processingsystems or remote printers or storage devices through interveningprivate or public networks. Modems, cable modem and Ethernet cards arejust a few of the currently available types of network adapters 1708.

The computer architecture 1700 may be coupled to storage 1716 (e.g., anytype of storage device; a non-volatile storage area, such as magneticdisk drives, optical disk drives, a tape drive, etc.). The storage 1716may comprise an internal storage device or an attached or networkaccessible storage. Computer programs 1706 in storage 1716 may be loadedinto the memory elements 1704 and executed by a processor 1702 in amanner known in the art.

The computer architecture 1700 may include fewer components thanillustrated, additional components not illustrated herein, or somecombination of the components illustrated and additional components. Thecomputer architecture 1700 may comprise any computing device known inthe art, such as a mainframe, server, personal computer, workstation,laptop, handheld computer, telephony device, network appliance,virtualization device, storage controller, etc.

ADDITIONAL EMBODIMENT DETAILS

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

What is claimed is:
 1. A computer program product, the computer program product comprising a computer readable storage medium having program code embodied therewith, the program code executable by at least one processor to perform: providing, by the at least one processor, a social media gateway interface with a plurality of adapters for each of multiple social media applications, wherein the social media gateway interface is between a data system and a social media bot of a plurality of social media bots, wherein a different social media bot is generated for each of the multiple social media applications for the data system, wherein a customizable mapping table is used to map messages between the data system and the multiple social media applications, wherein the data system comprises an Extract Transform and Load (ETL) server or a Master Data Management (MDM) server, and wherein the plurality of adapters comprise a smart phone adapter, a chat adapter, a microblogging service adapter, a social networking service adapter, a feeds adapter, and a wikis adapter; registering, by the at least one processor, at least one of the multiple social media applications for each event of multiple events that are from the ETL server or the MDM server; publishing, by the at least one processor, an event of the multiple events from the data system to the at least one of the multiple social media applications based on the registering; and using, by the at least one processor, the social media bot and one of the plurality of adapters to enable the data system to interact with the at least one of the multiple social media applications.
 2. The computer program product of claim 1, the computer program product comprising the computer readable storage medium having the program code embodied therewith, the program code executable by the at least one processor to perform: storing, by the at least one processor, the published event in a message queue.
 3. The computer program product of claim 1, wherein each event is published using an event gateway.
 4. The computer program product of claim 1, wherein the data system is one of the ETL server, the MDM server, a data store, and a data warehouse.
 5. A computer system, comprising: one or more processors, one or more computer-readable memories and one or more computer-readable, tangible storage devices; and program instructions, stored on at least one of the one or more computer-readable, tangible storage devices for execution by at least one of the one or more processors via at least one of the one or more memories, to perform operations, the operations comprising: providing a social media gateway interface with a plurality of adapters for each of multiple social media applications, wherein the social media gateway interface is between a data system and a social media bot of a plurality of social media bots, wherein a different social media bot is generated for each of the multiple social media applications for the data system, wherein a customizable mapping table is used to map messages between the data system and the multiple social media applications, wherein the data system comprises an Extract Transform and Load (ETL) server or a Master Data Management (MDM) server, and wherein the plurality of adapters comprise a smart phone adapter, a chat adapter, a microblogging service adapter, a social networking service adapter, a feeds adapter, and a wikis adapter; registering at least one of the multiple social media applications for each event of multiple events that are from the ETL server or the MDM server; publishing an event of the multiple events from the data system to the at least one of the multiple social media applications based on the registering; and using the social media bot and one of the plurality of adapters to enable the data system to interact with the at least one of the multiple social media applications.
 6. The computer system of claim 5, wherein the operations further comprise: storing the published event in a message queue.
 7. The computer system of claim 5, wherein each event is published using an event gateway.
 8. The computer system of claim 5, wherein the data system is one of the ETL server, the MDM server, a data store, and a data warehouse. 